Check if this issue is valid — if so, understand the root cause and fix it. At registry/registry.go, line 141:

<comment>RIR routing keys are duplicated across RDAP and WHOIS switch tables, creating drift risk and inconsistent fallback behavior over time.</comment>

<file context>
@@ -0,0 +1,171 @@
+	return ""
+}
+
+func rirRDAPBase(rir string) string {
+	switch strings.ToLower(rir) {
+	case "arin":
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At registry/rdap_pretty.go, line 220:

<comment>Parent entity `Public ID` lines are appended after recursive child rendering, so they can end up in a descendant’s section instead of the parent entity block.</comment>

<file context>
@@ -0,0 +1,250 @@
+	b.add("Registration", eventDate(e.Events, "registration"))
+	b.add("Last Changed", eventDate(e.Events, "last changed"))
+
+	for _, child := range e.Entities {
+		appendEntity(b, &child)
+	}
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At registry/whois.go, line 135:

<comment>WHOIS referral parsing is too narrow and misses `Whois Server:` style keys, which can prematurely stop referral-chain resolution.</comment>

<file context>
@@ -0,0 +1,159 @@
+			continue
+		}
+		switch key {
+		case "refer", "whois":
+			return value
+		case "referralserver":
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At registry/rdap.go, line 67:

<comment>RDAP formatter ignores `yaml` and returns pretty/JSON output despite CLI advertising YAML support.</comment>

<file context>
@@ -0,0 +1,84 @@
+
+func formatRDAP(resp *rdap.Response, format string) (string, error) {
+	switch strings.ToLower(format) {
+	case "json", "raw":
+		b, err := json.MarshalIndent(resp.Object, "", "  ")
+		if err != nil {
</file context>